home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
manage
/
tarchv.arc
/
TARCHIVE.TXT
< prev
next >
Wrap
Text File
|
1988-05-13
|
2KB
|
45 lines
TARCHIVE and TRESTORE may be used to backup and restore trustee
assignments for both users and groups with Netware.
TARCHIVE will get ALL User and Group Assignments for ALL attached
volumes and store them in a file called TARCHIVE.DAT. This data file can
then be backed up or transfered (or whatever).
TRESTORE will read the TARCHIVE.DAT file and add those assignments to
any existing trustee assignments. If there is a same definition, it will
update that trustee's privilages based upon those in TARCHIVE.DAT.
NOTE: TARCHIVE creates TARCHIVE.DAT in the default directory upon
execution.
TRESTORE looks for TARCHIVE.DAT in the default directory upon
execution.
The TARCHIVE.DAT file is a standard DOS delimited data file. I chose
this so that the TRESTORE program can be utilized even further. For
instance, a user can create (using any text editor) the TARCHIVE.DAT file
with the proper structure and TRESTORE will 'batch' assign these trustee
assignments. This allows the user to quickly type a large group of
assignments, and use TRESTORE to add them all at once.
The structure of TARCHIVE.DAT is quite simple and is defined below:
"<ObjectType>", "<ObjectName>", "<AccessMask>", "<TrusteePath>"
ObjectType = 1 for Users. 2 for Groups.
ObjectName = The User/Group Unique Object ID.
AccessMask = Privilages Granted in the form of RWOCDPSM.
This field MUST be properly aligned (8 characters).
A space MUST be used where a privilage is NOT
desired.
TrusteePath = This is the path to add the trustee to. The
syntax is VOLUME:PATH[/PATH...]
To see an example of the TARCHIVE.DAT file structure, run the TARCHIVE
program and then view the file. Please note, however, that aborting the
TARCHIVE program will also automatically purge the TARCHIVE.DAT file. The
program MUST terminate normally in order for it to be retained.
THIS PROGRAM WAS WRITTEN BY NETWARE USER MICHAEL SHADDUCK AND IS SUPPLIED
WITHOUT EXPRESSED OR IMPLIED WARRANTY AS TO ITS FITNESS OR FUNCTIONALITY.
5/13/88